Looks like the error occurs because emscripten-forge might be forcing the toolchain file, but we're building llvm-tblgen etc for the host correct ? This means we need to suppress it for 1st half and later we can restore the toolchain

Looks like the error occurs because emscripten-forge might be forcing the toolchain file, but we're building llvm-tblgen etc for the host correct ? This means we need to suppress it for 1st half and later we can restore the toolchain

By supress do you mean "unsetting the CMAKE_TOOLCHAIN_FILE" while building for host?

By supress do you mean "unsetting the CMAKE_TOOLCHAIN_FILE" while building for host?

Can possibly try that (passing empty string for the host rather than unsetting ?)

One small thing, I see this while building the llvm-tblgen

cmake -DLLVM_ENABLE_PROJECTS=clang -DLLVM_TARGETS_TO_BUILD=host -DCMAKE_BUILD_TYPE=Release ../llvm/ -DCMAKE_CROSSCOMPILING_EMULATOR=$BUILD_PREFIX/bin/node

I don't think we need the cross compiling emulator as we're building for host. Could you address this too ?

One small thing, I see this while building the llvm-tblgen

cmake -DLLVM_ENABLE_PROJECTS=clang -DLLVM_TARGETS_TO_BUILD=host -DCMAKE_BUILD_TYPE=Release ../llvm/ -DCMAKE_CROSSCOMPILING_EMULATOR=$BUILD_PREFIX/bin/node

I don't think we need the cross compiling emulator as we're building for host. Could you address this too ?

Done

Thanks for the changes, here hopefully everything build fine.

Hey @kr-2003,

Through conda-forge (or through any llvm release) ,

We won't be having direct access to clang-tblgen. Here's the reason why the llvm-tblgen binary is provided but clang-tblgen is not !

https://discourse.llvm.org/t/clang-tblgen-not-installed/52997

Which means we need to build our own llvm-tblgen and clang-tblgen !

So we need to move along the lines of what you've done

1. we deactivate the script
2. build what we need for the build arch
3. activate the script
4. Build llvm

Hey @anutosh491,

Thanks.

I have pushed the changes. Made two new scripts (i.e. activats.sh and deactivate.sh) inside the recipe-directory.

Hey @DerThorsten,

Should each recipe have their own activation/deactivation scripts? Is it possible for us to use the scripts under /recipes/recipes/emscripten_emscripten-wasm32 in recipes/recipes_emscripten/llvm/build.sh.

Hey @DerThorsten,

Should each recipe have their own activation/deactivation scripts? Is it possible for us to use the scripts under /recipes/recipes/emscripten_emscripten-wasm32 in recipes/recipes_emscripten/llvm/build.sh.

I think in general, we want to avoid activation scripts when possible.
It might be possible to call the de-activation script by hand, but its a hack.

Also I am a bit unsure why we need to add new

Hey @kr-2003,

Through conda-forge (or through any llvm release) ,

We won't be having direct access to clang-tblgen. Here's the reason why the llvm-tblgen binary is provided but clang-tblgen is not !

https://discourse.llvm.org/t/clang-tblgen-not-installed/52997

Which means we need to build our own llvm-tblgen and clang-tblgen !

So we need to move along the lines of what you've done

1. we deactivate the script
2. build what we need for the build arch
3. activate the script
4. Build llvm

if you build for the "build-arch" then there is no emscripten whatsoever. So why would you need to do any disabling of activation scripts?

if you build for the "build-arch" then there is no emscripten whatsoever. So why would you need to do any disabling of activation scripts?

Yes, correct. My bad. I have moved llvm-tblgen and clang-tblgen to be built under llvm-tblgen pkg name in "build-arch". And then using this build with llvm-empscripten build.

Hey @kr-2003,

Thanks for the changes here. Now that this has gone in, we need to test if this llvm build is working as per what we want.
As a follow up

1. Fetch latest llvm locally once hosted (should take about 2 hours), build cppinterop on top of it and run the emscripten tests. All tests should pass as expected
2. Once that is done, update cppinterop's recipe to use this llvm build (you would just need to increment the build number by 1)

Ping me once this is done.

Hey @kr-2003,

Thanks for the changes here. Now that this has gone in, we need to test if this llvm build is working as per what we want. As a follow up

1. Fetch latest llvm locally once hosted (should take about 2 hours), build cppinterop on top of it and run the emscripten tests. All tests should pass as expected
2. Once that is done, update cppinterop's recipe to use this llvm build (you would just need to increment the build number by 1)

Ping me once this is done.

Its working 🚀 .